Skip to Content.
Sympa Menu

ndt-users - Re: Server unable to determine bottleneck link type

Subject: ndt-users list created

List archive

Re: Server unable to determine bottleneck link type


Chronological Thread 
  • From: "Nathan C. Broome" <>
  • To: Richard Carlson <>
  • Cc:
  • Subject: Re: Server unable to determine bottleneck link type
  • Date: Thu, 30 Aug 2007 13:44:12 -0400

Rich,


Thank you, that was it. There are two interfaces on this machine. I forced it to eth1 and it is now working properly.



Thanks,


Nathan


Richard Carlson wrote:
Nathan;

It looks like the server process (web100srv) is looking at the wrong interface (e.g., eth0 instead of eth1). Does this server have multiple Ethernet NIC's? If so, is the web100srv process looking at the correct interface? You can use the '-i ethx' option to specifically set the interface.

Rich

At 09:04 AM 8/30/2007, Nathan C. Broome wrote:
Hello,

I've recently installed NDT 3.4.1 with web100 2.5.16, on linux kernel 2.6.22, running on Suse Linux Enterprise Server 10.


The test is reporting the following error:

"Server unable to determine bottleneck link type"

When clicking the More Details button I get the following text:


Client Data reports link is 'System Fault', Client Acks report link is 'System Fault'
Server Data reports link is 'System Fault', Server Acks report link is 'System Fault'


Any ideas what the problem might be? Any assistance is appreciated.


Thanks,

Nathan Broome
Network Administrator
Oberlin College






------------------------------------



Richard A. Carlson e-mail:
Network Engineer phone: (734) 352-7043
Internet2 fax: (734) 913-4255
1000 Oakbrook Dr; Suite 300
Ann Arbor, MI 48104




Archive powered by MHonArc 2.6.16.

Top of Page