[ofw] ping on WinOF

[Tzachi Dar]

I haven't seen such behavior.
 
Can you please run with wireshark on both sides and send us the logs.
 
Thanks
Tzachi


________________________________

	From: ofw-bounces at lists.openfabrics.org
[mailto:ofw-bounces at lists.openfabrics.org] On Behalf Of David Brean
	Sent: Wednesday, July 01, 2009 6:39 PM
	To: ofw at lists.openfabrics.org
	Subject: [ofw] ping on WinOF
	
	
	Hello,
	
	An internal customer is using WinOF 2.0.X and has reported to me
the following behavior related to IPoIB and ping:
	
	Do you have any ideas on why windows 2008 client with HCA may
first timeout ping to other clients on the fabric?
	
	Initially ping fails but then starts working.
	
	Example :  Ping is invoked three times successfully.
	
	C:\GRITS>ping -a 192.168.100.235
	
	Pinging 192.168.100.235 with 32 bytes of data:
	Request timed out.
	Request timed out.
	Request timed out.
	Request timed out.
	
	Ping statistics for 192.168.100.235:
	   Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
	
	C:\GRITS>ping -a 192.168.100.235
	
	Pinging 192.168.100.235 with 32 bytes of data:
	Request timed out.
	Request timed out.
	Reply from 192.168.100.235: bytes=32 time<1ms TTL=255
	Reply from 192.168.100.235: bytes=32 time<1ms TTL=255
	
	Ping statistics for 192.168.100.235:
	   Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
	Approximate round trip times in milli-seconds:
	   Minimum = 0ms, Maximum = 0ms, Average = 0ms
	
	C:\GRITS>ping -a 192.168.100.235
	
	Pinging 192.168.100.235 with 32 bytes of data:
	Reply from 192.168.100.235: bytes=32 time<1ms TTL=255
	Reply from 192.168.100.235: bytes=32 time<1ms TTL=255
	Reply from 192.168.100.235: bytes=32 time<1ms TTL=255
	Reply from 192.168.100.235: bytes=32 time<1ms TTL=255
	
	Ping statistics for 192.168.100.235:
	   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
	Approximate round trip times in milli-seconds:
	   Minimum = 0ms, Maximum = 0ms, Average = 0ms
	
	Then we are good for sometime before this starts again if
network is idle on the fabric.
	
	Has this sort of behavior been observed before?  The Linux and
Solaris nodes sharing the same IP subnet appear to be behaving normally.
Windows server is the "out-of-the-box" configuration with Voltaire
switch configured with only the default partition (0xFFFF).
	
	-David
	
	

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/ofw/attachments/20090701/33edf923/attachment.html>