× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Yes I have seen it, and I don't understand what the VIOS developers
specifically put that landmine into the defaults for you to step on. It's
like they enjoy the support call and hearing the pain on the other end of
the line.

I've gotten by it by always setting the LSO when I configure the SEA. On
the HMC (even the new interface surprisingly) it's easy to do, then the
problem does not bite later.


--
Jim Oberholtzer
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Mitchell, Dana
Sent: Friday, August 24, 2018 2:13 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: LSO and VIOS SEA mismatch

I just completed another migration from p8->p9 and ran into this problem
again. Newly created SEAs on dual VIOs default to Largesend=0. When the
I LPARs come up they default to Largesend turned on. This mismatch causes
dropped packets that results in sessions hanging randomly and being
generally unusable. Largesend can be disabled on the IBMi side with some
SST gyrations, but only lasts for the current IPL, after re-IPL it goes
back. LSO can be turned on the SEA with VIOS command that should be
relatively permanent. Currently 7.2 TR8 Vios 2.2.6.21

I'm wondering why with P9 the mismatch happens? Anybody else run into this?


Dana

Attention: This electronic document and associated attachments (if any) may
contain confidential information of the sender (SHAZAM Network) and is
intended solely for use by the addressee(s). Review by unintended
individuals is prohibited. If you are not the intended recipient: (i) do not
read, transmit, copy, disclose, store, or utilize this communication in any
manner; (ii) please reply to the sender immediately, state that you received
it in error and permanently delete this message and any attachment(s) from
your computer and destroy the material in its entirety if in hard copy
format. If you are the intended recipient, please use discretion in any
email reply to ensure that you do not send confidential information as we
cannot secure it through this medium. By responding to us through internet
e-mail, you agree to hold SHAZAM, Inc. and all affiliated companies harmless
for any unintentional dissemination of information contained in your
message. Thank you.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.