Logo_Vet

Tester,
Please confirm you made Registry Edit changes only on CLIENT ( aka DUT2).


--
From HCT to DTM to WLK I ''''''''v gone thru all the kits has shipped..



"Tester" wrote:

> Thanks again for the prompt response,, ... Please find detail configuration
> information I have in my LAB:
>
> I have that reg settings. I have two identical systems which I can use as a
> DUTs. DTM controller is different system. Studio is on Controller itself. As
> you mentioned I have two interfaces, WSD has its own ether interface. These
> two DUTs are connected back to back with WSD interface. Normal ethernet
> interface on which [DTM studio*DTM controller*DUTs] talk is on corporate LAN.
>
> I could able to reach upto WSD device test submission process in studio GUI,
> but after that once I come back to DeviceConsole TAB, I am confused about:
>
> 1. How to inform DTM that use 'DUT1' as a server, 'DUT2' as a client and
> start these WSD submission process in between these two systems(DUTs).
> Currently I am getting only list of WSD inteface, normal ether itneface
> etc... my driver files..etc...
>
> As of now only one doubt....
>
> Thanks,
>
>
> "Logo_Vet" wrote:
>
> > Congratulations Tester ..Installing WLK is an achievement in itself..
> > good Luck for your Testing!!
> >
> > I'm not into winsock testing ,so I can't comment on what mistakes you
> > made..But going by your comments, here's my views:
> > -You do not need any additional MCU policy.
> > -INf should be located in a shared folder and when prompted, you should be
> > able to share it / install it.
> >
> > There are some pre-requisites (preparations) before submission process..
> > There is a very important registry key as given below.. I presume you know
> > this info..same has been reproduced below just in case you missed it :
> >
> > You must have two identical computers. These computers should be dual homed.
> > That is, you should have one WSD/SDP-capable device and another Ethernet
> > interface for message traffic between the nodes. You must have a third
> > computer to run the DTM server.
> > Note : You can connect WSD/SDP-capable devices back-to-back or by using a
> > switch to provide connectivity.
> >
> > The DTM network gatherer can discover RDMA-capable devices only if the
> > miniport registry entry contains a DWORD value that is named RDMACapable that
> > has a value of 1. You can set this value manually or through the INF file. If
> > you write this entry to the registry by using the INF file, remember that
> > this entry is a test requirement and the release version of the INF file does
> > not have to have this entry.
> >
> > After you create the RDMACapable registry entry (manually or through the INF
> > file), restart WTTClient (DTM client). You can reboot or perform a service
> > restart to restart WTTClient.
> >
> > --
> > From HCT to DTM to WLK I ''''''''v gone thru all the kits has shipped..
> >
> >
> >
> > "Tester" wrote:
> >
> > > Thanks for the wonderful help, now I am able to install DTM successfully ...
> > >
> > > Some queries on Winsock Direct test procedure:
> > > 1. Do I need to add any other MCU Policy other than WDK\ConfigureRDMACapable ?
> > > 2. I am testing for the Network Ethernet 10Gbps Network Card. So do my INF
> > > is suppose to be installed prior to starting this submission test? If no than
> > > while following the steps provided by you after giving submission name/pool
> > > selection in the last step it gives messageas as there are no devices to run
> > > this test. Still I continued to process that and as per your steps it doesnt
> > > showed any devices list on left side of Device console and I could not follow
> > > any of the steps provided by you under "Run the tests:" section.
> > >
> > > Please help I guess still I am making some crucial mistake....
> > >
> > > Thanks again for the wonderful help you have provided,...
> > > Tester.
> > >
> > >
> > > "Logo_Vet" wrote:
> > >
> > > > Tester,
> > > > thankyou for your feedback.. Have you installed WLK 1.0.c ?
> > > >
> > > > Main thing is settingup MCU Policy ->RDMACapable
> > > >
> > > > Here are steps you need to do->taken from 1.0.0c docs -unedited :
> > > >
> > > > On the Explorers menu, click Job Monitor.
> > > > Right-click Machine Pool Root ($), and then click Add Machine Pool.
> > > > Right-click the new machine pool, and then click Properties.
> > > > Click the MCU Policy tab, and then select WDK\ConfigureRDMACapable.
> > > >
> > > > Click Add and then click OK.
> > > > Move your client machines from the “Default Pool” to the new machine pool.
> > > > Right-click each computer in the new pool, point to Change Status, and then
> > > > click Reset. The computers should change status to Ready.
> > > > On the Explorers menu, click Device Console.
> > > > In the Submission list, click New Submission.
> > > > Select the client operating system, and then click Next.
> > > > Select Device Submission, and then click Next.
> > > > Select Network > WinsockDirect, and then click Next.
> > > > Select Basic, and then click Next.
> > > > Enter a new name for Submission Name and associate it with a machine pool
> > > > name where you are going to run the logo tests, and then click Next.
> > > > Locate the driver INF files that you are testing, and then click Load. You
> > > > might have to perform several iterations. After you are finished with all INF
> > > > files, click Next.
> > > >
> > > > On the left side, Device Console should then display the devices that it
> > > > discovered.
> > > > Run the tests:
> > > > Select the device to run the logo tests on.
> > > > Right-click the test that you want to run, and then click Add Information.
> > > > Select a “messaging device” for the test computer.
> > > > Select a “support device” for the remote computer. This device is the device
> > > > that is connected to the test device.
> > > > Select a “messaging device” for the remote computer.
> > > > Save the submission.
> > > > Click Add Selected, and then click Schedule.
> > > >
> > > > You can follow the progress of the test by using Job Monitor.
> > > > After all the tests are run (including NDISTests and Driver Reliability),
> > > > right-click the tree that is displayed on the left side of Device Console,
> > > > and then click Create CPK.
> > > > Command Syntax
> > > >
> > > > --
> > > > From HCT to DTM to WLK I ''''''''v gone thru all the kits has shipped..
> > > >
> > > >
> > > >
> > > > "Tester" wrote:
> > > >
> > > > > Thats gr8... it seems that you have good exposure on WLK.
> > > > > Can you help me in locating winsock tests in WLK1.0.c and running them on
> > > > > Ethernet LAN network card?
> > > > >
> > > > > Thanks,
> > > > >
> > > > > "Logo_Vet" wrote:
> > > > >
> > > > > > Tester,
> > > > > > WLK 1.0.c is THE TESTKIT till they release d-e-f or x -y -z...
> > > > > >
> > > > > >
> > > > > > --
> > > > > > From HCT to DTM to WLK I ''''''''v gone thru all the kits has shipped..
> > > > > >
> > > > > >
> > > > > >
> > > > > > "Tester" wrote:
> > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > I could able to submit specific test cases now. Thanks for this information.
> > > > > > >
> > > > > > > Anyways, now after this all research I found that it has not yet solved my
> > > > > > > problem of testing winsock direct component of SAN (system area network)
> > > > > > > category tests.
> > > > > > >
> > > > > > > From some online docs i found that winsock direct became obsolete now from
> > > > > > > DTM and may come in WLK.... is this correct information?
> > > > > > >
> > > > > > > If so that which WLK I can download and use for this purpose?
> > > > > > > There are wlk_1.0.a, wlk_1.0.b, wlk_1.0.c etc... versions available on
> > > > > > > Microsoft's web site.
> > > > > > >
> > > > > > > Thanks,
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > "Logo_Vet" wrote:
> > > > > > >
> > > > > > > > Folks,
> > > > > > > > I regret I missed the forum for couple of days.. I have seen similar(not
> > > > > > > > exactly same) issues but my client was running XP in non-english language and
> > > > > > > > all english clients were configuring fine.. funny ..but my guess is non
> > > > > > > > english Os had some network protocols set as default which was not liked by
> > > > > > > > DTM controller..
> > > > > > > > .. The issue here seems to be network settings related.. so here is the
> > > > > > > > workaround ( its not documented anywhere in help docs) , based on my test
> > > > > > > > experience.. It worked for my environment ,and is simple to try.. Hope it
> > > > > > > > does the trick for all.
> > > > > > > > Step 1: Ensure all network related HW is in perfect condition.
> > > > > > > > Step 2: configure DTM controller and then make it DHCP Server ( don't
> > > > > > > > install DTM to DHCP server it won't work..instead configure DTM controller
> > > > > > > > first and then add DHCP role to it. )
> > > > > > > > Step 3: Add Studio role to controller box or add additional box if you so
> > > > > > > > desire.
> > > > > > > > Step 4: Add one DTM Client to it and configure it as per my earlier thread.
> > > > > > > >
> > > > > > > > NOTE for Existing clients if trying to re-install /re-configure on same
> > > > > > > > controller: Delete existing submissions from Device console as well as Job
> > > > > > > > Monitor first, before adding it to default machine pool.
> > > > > > > >
> > > > > > > > --
> > > > > > > > From HCT to DTM to WLK I ''''''''v gone thru all the kits has shipped..
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > "Don Burn" wrote:
> > > > > > > >
> > > > > > > > > Thomas,
> > > > > > > > >
> > > > > > > > > Be sure to get whether the system WHQL'ed for Server or Client. This
> > > > > > > > > is the problem with a large number of the workstation systems they actually
> > > > > > > > > have a server motherboard, which means client tests may not pass. This
> > > > > > > > > happens for instance with all the workstations that you can get through the
> > > > > > > > > AMD software developer program.
> > > > > > > > >
> > > > > > > > > The real solution is to have Microsoft designate the type of
> > > > > > > > > certification the component or the sytem recieved.
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Don Burn (MVP, Windows DDK)
> > > > > > > > > Windows 2k/XP/2k3 Filesystem and Driver Consulting
> > > > > > > > > Website: http://www.windrvr.com
> > > > > > > > > Blog: http://msmvps.com/blogs/WinDrvr
> > > > > > > > > Remove StopSpam to reply
> > > > > > > > >
> > > > > > > > > "Thomas F. Divine" <tdivine@NOpcausaSPAM> wrote in message
> > > > > > > > > news:%23XsInbIpHHA.4192@TK2MSFTNGP06.phx.gbl...
> > > > > > > > > > I'd like to hear recommendations for good DTM Client machines from
> > > > > > > > > > Logo_Vet and other professional testers.
> > > > > > > > > >
> > > > > > > > > > Small shops like mine can't afford to buy and throw away machines that
> > > > > > > > > > are unsuitable (e.g., can't support a needed power state, etc.).
> > > > > > > > > >
> > > > > > > > > > Thomas F. Divine
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >