Bad guess: the MTU used by VSE on this Hipersocket link is not 1500 (as
found as default on the www), a query show 8192, same as in Linux
Digging further.
2010/3/29 Kris Buelens
> OK Thanks, know what to look at tomorrow.
>
> 2010/3/29 David Boyes
>
>
>> We just found out that the defined M
OK Thanks, know what to look at tomorrow.
2010/3/29 David Boyes
>
> We just found out that the defined MTU's differ, and I always heard that
> MTU sizes should be identical:
>
>
>
> Unless path discovery is active on both ends of the link, the sizes should
> be identical.
>
>
> Might this be an
We just found out that the defined MTU's differ, and I always heard that MTU
sizes should be identical:
Unless path discovery is active on both ends of the link, the sizes should be
identical.
Might this be an explanation? How comes it works fine (most of the time) with
apparently different
>>> On 3/29/2010 at 12:28 PM, Kris Buelens wrote:
> Might this be an explanation? How comes it works fine (most of the time)
> with apparently different MTU values?
Absolutely it could be the problem. It will only fail if a packet exceeding
the MTU gets sent, so if your traffic is mainly pack
Not really VM, but z/VSE and Linux
A customer I inherited encounters intermittent hangs of their VSE DRDA
connection to UDB on Linux on system z. When they restart TCP/IP VSE all
goes well again, for weeks or (lately: for a couple of days). The VSE
system runs under VM on standard engines and Li
