<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18702"></HEAD>
<BODY bgColor=#ffffff text=#000000>
<DIV><SPAN class=376294015-01072009><FONT color=#0000ff size=2 face=Arial>I
haven't seen such behavior.</FONT></SPAN></DIV>
<DIV><SPAN class=376294015-01072009><FONT color=#0000ff size=2
face=Arial></FONT></SPAN> </DIV>
<DIV><SPAN class=376294015-01072009><FONT color=#0000ff size=2 face=Arial>Can
you please run with wireshark on both sides and send us the
logs.</FONT></SPAN></DIV>
<DIV><SPAN class=376294015-01072009><FONT color=#0000ff size=2
face=Arial></FONT></SPAN> </DIV>
<DIV><SPAN class=376294015-01072009><FONT color=#0000ff size=2
face=Arial>Thanks</FONT></SPAN></DIV>
<DIV><SPAN class=376294015-01072009><FONT color=#0000ff size=2
face=Arial>Tzachi</FONT></SPAN></DIV><BR>
<BLOCKQUOTE
style="BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> ofw-bounces@lists.openfabrics.org
[mailto:ofw-bounces@lists.openfabrics.org] <B>On Behalf Of </B>David
Brean<BR><B>Sent:</B> Wednesday, July 01, 2009 6:39 PM<BR><B>To:</B>
ofw@lists.openfabrics.org<BR><B>Subject:</B> [ofw] ping on
WinOF<BR></FONT><BR></DIV>
<DIV></DIV>Hello,<BR><BR>An internal customer is using WinOF 2.0.X and has
reported to me the following behavior related to IPoIB and ping:<BR><BR><I>Do
you have any ideas on why windows 2008 client with HCA may first timeout ping
to other clients on the fabric?<BR><BR>Initially ping fails but then starts
working.<BR><BR>Example : Ping is invoked three times
successfully.<BR><BR>C:\GRITS>ping -a 192.168.100.235<BR><BR>Pinging
192.168.100.235 with 32 bytes of data:<BR>Request timed out.<BR>Request timed
out.<BR>Request timed out.<BR>Request timed out.<BR><BR>Ping statistics for
192.168.100.235:<BR> Packets: Sent = 4, Received = 0, Lost = 4
(100% loss),<BR><BR>C:\GRITS>ping -a 192.168.100.235<BR><BR>Pinging
192.168.100.235 with 32 bytes of data:<BR>Request timed out.<BR>Request timed
out.<BR>Reply from 192.168.100.235: bytes=32 time<1ms TTL=255<BR>Reply from
192.168.100.235: bytes=32 time<1ms TTL=255<BR><BR>Ping statistics for
192.168.100.235:<BR> Packets: Sent = 4, Received = 2, Lost = 2
(50% loss),<BR>Approximate round trip times in milli-seconds:<BR>
Minimum = 0ms, Maximum = 0ms, Average = 0ms<BR><BR>C:\GRITS>ping -a
192.168.100.235<BR><BR>Pinging 192.168.100.235 with 32 bytes of data:<BR>Reply
from 192.168.100.235: bytes=32 time<1ms TTL=255<BR>Reply from
192.168.100.235: bytes=32 time<1ms TTL=255<BR>Reply from 192.168.100.235:
bytes=32 time<1ms TTL=255<BR>Reply from 192.168.100.235: bytes=32
time<1ms TTL=255<BR><BR>Ping statistics for
192.168.100.235:<BR> Packets: Sent = 4, Received = 4, Lost = 0 (0%
loss),<BR>Approximate round trip times in milli-seconds:<BR>
Minimum = 0ms, Maximum = 0ms, Average = 0ms<BR><BR>Then we are good for
sometime before this starts again if network is idle on the
fabric.<BR></I><BR>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).<BR><BR>-David<BR><BR></BLOCKQUOTE></BODY></HTML>