* Eilon Greenstein

quoted text
> This message indicates that for over 1 second, the device could not 
> transmit anything to the network (the same packet was not
> transmitted for over one second) - this usually happens when the
> network is in fatal condition - usually because some device is
> sending constant pause stream that halts all traffic. In this case,
> the device is incrementing the counter and drains outgoing traffic -
> without this action, the device will not be able to unload since even
> the commands from the driver will not be processed due to this
> excessive back pressure.
> 
> As you indicated - once you remove the server that halts all other 
> traffic, everything else resumes - that indicates that this server
> is sending constant pause that ultimately halts the entire switch.

Thank you very much for your input Elion, you've definetively helped me
look in the right place.  I do see a constant stream of pause frames
being sent by the switch module to a F5 BIG-IP box that's connected to
external ports of the switch.  The stream appears instantly when the ESX
server is connected and vanishes just as fast when it's been
disconnected.  I haven't been able to verify what the ESX server is
doing to the switch yet, but your assumption that it too is spewing out
pause frames sounds very likely to me.

However I'm still a bit confused on why this is triggering the "NIG
timer max" message on the Linux blade.  It would have made perfect sense
to me for the bnx2x driver/NIC to stop transmitting outbound frames if
it was the recipient of an inbound pause frame flood, but tcpdump does
not show any such frames being received.  Yet it stalls all outbound
traffic.  Any idea why?

Best regards,
-- 
Tore Anderson
Redpill Linpro AS - http://www.redpill-linpro.com/
Tel: +47 21 54 41 27
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html